Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[VMC] Adding/Removing AD groups to the CloudAdminGroup via apiexplorer (56489)

Last Updated: 10/2/2023Categories: TroubleshootingTotal Views: 10394Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

This article lists out the steps to modify group membership of the CloudAdminGroup on the Cloud vCenter in VMware Cloud on AWS

Purpose

Detail how to add LDAP Groups to the CloudAdminGroup via API Explorer.

Cause

Customer is missing permissions for a specific LDAP User/Group but [email-masked] account has the required permissions.

Impact / Risks

Customers may be blocked from integrating or performing actions with LDAP User/Groups.
This process can only be used to add AD Groups to the CloudAdminGroup, this will not work for adding specific AD Users.

Resolution

Login into https://<Cloud_VC_FQDN>/apiexplorer/ Use the cloudadmin ID to login

Navigate to hvc/management/administrators and click on Show/Hide

Use the GET hvc/management/administrators API to find the current members of the CloudAdminGroup

Click on Execute to run the GET request. The response will be in JSON format.

To add an AD group use the POST hvc/management/administrators?action=add API

In the request_body put the AD group name in the format {“group_name”: ”[email-masked]”}. You only need to modify the [email-masked] section, leave group_name alone.

{
"group_name": "[email-masked]"
}

Click on Execute. If the Response Code comes as 204 or 200, That means the group has been added.

Note: You can then use the GET API again (mentioned above) to fetch the group list to verify if the group has been added or not.

If you want to remove an AD group from the CloudAdminGroup

Use the  POST /hvc/management/administrators?action=remove API

In the request_body put the AD group name in the format “group_name”: ”[email-masked]”

{
"group_name": "[email-masked]"
}

Click on Execute.

If the Response Code is 204 or 200, that means the group has been removed successfully

To verify, Do a GET request again to see the current group membership and you will see that the group has been removed.

Workaround

Use [email-masked].

Related Information

VMware Developer Documentation

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant